Systems, methods, and devices for tracking a shipment using a wireless tracker

ABSTRACT

Embodiments of the present disclosure include systems, methods, and devices for tracking a shipment using a wireless tracker. In such embodiments, the wireless tracker determines a location of the wireless tracker device and regulates battery usage of wireless tracker based on the location. In addition, the wireless tracker is configured to determine a current location of the wireless tracker device at one or more intervals such that the one or more intervals are based on a delivery route of the shipment. Moreover, the wireless tracker is configured to receive and verify one or more codes to for a chain of custody of the shipment. Also, the wireless tracker is configured to determine a trigger event based on the location of the wireless tracker device and/or sensor information as well as send a notification to a computer server based on the trigger event.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority under the laws and rules of theUnited States, including 35 USC §120, to U.S. Patent Application No.61/951,555 filed on Mar. 12, 2014. The contents of U.S. PatentApplication No. 61/951,555 filed on Mar. 12, 2014 is herein incorporatedby reference in its entirety.

BACKGROUND

Conventional tracking systems provide the ability for a company tolocate human and/or material assets on demand whether it is indoors,outdoors or in transit. This capability allows the company to improveits quality of service, engendering improved customer satisfaction. Suchconventional tracking systems use GPS/GSM tracking devices but theseconventional tracking systems have several limitations that include butare not limited to the following. First, a tracking device owner doesnot have the ability to retrieve the tracking device once the asset thatis being tracked/shipped has reached its destination. For example, inthe context of a package shipped to New York from California via theUnited States Postal Service (USPS), the tracking device owner placesthe tracking device in the package to obtain location updates but uponreaching the destination the tracking device owner does not have theability to have the tracking device returned to a desired location. Thetracking device owner does not have the ability to define a new trackingdestination or reuse the tracking device for a new destination uponarrival to the destination. In certain situation, if the origin of theshipment is not the origin of the tracking device owner, then the ownerhas to first ship the device to the origin of the shipment, typically a3^(rd) party logistics providers or their remote warehouse or theirsupplier locations, instruct them to include the tracking device intheir desired shipment and once it reaches the destination, have to beresponsible to retrieve it back to their main location.

Second, the tracking device provides current known locations atpre-defined update intervals and user defined geographic boundaries toprovide location updates. Location updates may not be provided if anevent occurs between two update intervals. For example, a user definesan alert condition when asset enters and exits a specified geographicboundary at an update interval of 30 minutes. If the asset enters andexits the specified geographic boundary within 30 minutes then thetracing device fails to provide an update.

Third, the conventional tracking devices have built-in batteries thatare charged via a power supply. The consumption of battery power isdirectly proportional to the number of location updates the trackingdevice provides or power consumption of other tracker components. Manytracking applications become infeasible because the user requiresfrequent updates or frequent use of other components that exhaustbattery life.

Fourth, a conventional tracking device provides updates to the deviceowner and relies on such updates to disseminate that update informationto other users who are interested in following that asset being tracked.

Fifth, a conventional tracking device does not have the ability toauthenticate and verify whether the asset/shipment coupled to thetracking device has been delivered to a destination and a chain ofcustody of the asset was not compromised. Such authentication mayinvolve confirming the identity of an asset/shipment by a person or amodule that traces the origins of the asset/shipment, or ensuring thatthe packaging or labeling of the asset/shipment is what it claims to be.Authentication often involves verifying the validity of at least oneform of identification. Authentication further involves comparing theattributes of the asset itself to what is known about asset's origin.For example, consumer goods such as pharmaceuticals, perfume, fashionclothing may use authentication to prevent original goods replaced bycounterfeit goods.

Sixth, a conventional tracking device does not have the ability toreport tampering such as separating the tracking device from the trackedgoods. Seventh, a conventional tracking device does not have the abilityof multi-dimensional tracking such as to determine and provide theability to configure the rules of tracking based on, but not limited to,if-else-while of various parameter such as speed, altitude, temperature,pressure, location and change the behavior of tracking For example,international tracking intervals is changed while at sea, dynamicallychanging the tracking geo-boundaries and conditions.

Eight, a conventional tracking device does not have the ability toassociate with the shipment order information and hence requires usersto track the devices by their IDs instead of the shipment orderinformation which includes but not limited to order number, purchaseorder number, Serial Shipment Container Code (SSCC), Billing of Ladingnumber, Lorry Receipt (LR) number, Shipment Manifest number and others.For example, an order no. A345 may have 100 pallets and each pallet hasa conventional tracking device. In order, to track order no. A345, theuser needs to know the entire 100 conventional tracker IDs and track bytheir IDs.

Ninth, a conventional tracking device does not provide the condition ofthe shipment in transit such as if the shipment is not within itsshipping temperature, humidity, moisture limits, or if the shipment wasmoved from one transport carrier to another, or the shipment was nothandled properly.

Accordingly, there is a need for systems, methods, and devices forimproved techniques to track an asset/shipment from any origin to anydestination using a tracking device such that a tracking device can bereturned to the tracking devices owner as well as the tracking deviceprovides location and condition updates at useful intervals. Further,the tracking device has improved management of battery life, as well asthe system allows a tracking device to take action based on updateinformation provided by the tracking device, and authenticate the assetcoupled to the tracking device to verify chain of custody. In addition,the tampering of the tracking device/wireless tracker andconditional/multi-dimensional tracking need to be addressed.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The accompanying figures, where like reference numerals refer toidentical or functionally similar elements throughout the separateviews, together with the detailed description below, are incorporated inand form part of the specification, and serve to further illustrateembodiments of concepts that include the claimed invention, and explainvarious principles and advantages of those embodiments.

FIG. 1 is a functional block diagram of a system for tracking ashipment/asset using a wireless tracker, in accordance with someembodiments.

FIGS. 2A-2B are functional block diagrams of a wireless tracker, inaccordance with some embodiments.

FIGS. 3-4 are functional block diagrams of devices used in tracking ashipment/asset using a wireless tracker, in accordance with someembodiments.

FIGS. 5A-5C are flowcharts that illustrates methods for tracking ashipment/asset using a wireless tracker, in accordance with someembodiments.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity and have not necessarily beendrawn to scale. For example, the dimensions of some of the elements inthe figures may be exaggerated relative to other elements to help toimprove understanding of embodiments of the present invention.

The apparatus and method components have been represented whereappropriate by conventional symbols in the drawings, showing only thosespecific details that are pertinent to understanding the embodiments ofthe present invention so as not to obscure the disclosure with detailsthat will be readily apparent to those of ordinary skill in the arthaving the benefit of the description herein.

DETAILED DESCRIPTION

The illustrative embodiments described in the detailed description,drawings, and claims are not meant to be limiting. Other embodiments maybe utilized, and other changes may be made, without departing from thescope of the subject matter presented herein. It will be readilyunderstood that the aspects of the present disclosure, as generallydescribed herein, and illustrated in the Figures, can be arranged,substituted, combined, separated, and designed in a wide variety ofdifference configurations, all of which are explicitly contemplatedherein. Further, in the foregoing description, numerous details are setforth to further describe and explain one or more embodiments. Thesedetails include system configurations, block module diagrams, flowcharts(including transaction diagrams), and accompanying written description.While these details are helpful to explain one or more embodiments ofthe disclosure, those skilled in the art will understand that thesespecific details are not required in order to practice the embodiments.

As will be appreciated by one skilled in the art, aspects of the presentdisclosure may be embodied as an apparatus that incorporates somesoftware components. Accordingly, some embodiments of the presentdisclosure, or portions thereof, may combine one or more hardwarecomponents such as microprocessors, microcontrollers, or digitalsequential logic, etc., such as processor with one or more softwarecomponents (e.g., program code, firmware, resident software, micro-code,etc.) stored in a tangible computer-readable memory device such as atangible computer memory device, that in combination form a specificallyconfigured apparatus that performs the functions as described herein.These combinations that form specially-programmed devices may begenerally referred to herein as “modules”. The software componentportions of the modules may be written in any computer language and maybe a portion of a monolithic code base, or may be developed in morediscrete code portions such as is typical in object-oriented computerlanguages. In addition, the modules may be distributed across aplurality of computer platforms, servers, terminals, mobile devices andthe like. A given module may even be implemented such that the describedfunctions are performed by separate processors and/or computing hardwareplatforms.

Embodiments of the present disclosure include systems, methods, anddevices for tracking a shipment or asset using a wireless tracker. Insuch embodiments, the wireless tracker determines a location of thewireless tracker device and regulates battery usage of wireless trackerbased on the location. Further, in such embodiments, the wirelesstracker may have one or more panels that include a sender address,sender postage, recipient address, or recipient postage such that thewireless tracker is delivered from the recipient address to trackingdevice owner. In addition, the wireless tracker is configured todetermine a current location of the wireless tracker device at one ormore intervals such that the one or more intervals are based on adelivery route of the shipment. Moreover, the wireless tracker isconfigured to receive and verify one or more codes to for a chain ofcustody of the shipment. Also, the wireless tracker is configured todetermine a trigger event based on the location of the wireless trackerdevice and/or sensor information as well as send a notification to acomputer server based on the trigger event.

FIG. 1 is a functional block diagram of a system 100 for tracking ashipment using a wireless tracker, in accordance with some embodiments.Such a system 100 includes one or more computer servers 102 that mayhost a web portal 104 or other user portal. A user device (114-116) suchas a smartphone, tablet computer, laptop computer, and desktop computermay access the web portal 104 over the Internet 108. Alternatively, auser device 114 may access the computer server(s) 102 across a mobilenetwork 106. In addition, a shipment with a wireless tracker 112 may beon a shipping transportation vehicle 110 and is in communication withthe computer server(s) 102 over the mobile network 106. Such a systemmay be used by a shipping delivery company or a company that frequentlyships various assets among the company's facilities that are separatedby geographic distances.

The system 100 allows a shipment order to be automatically generated bythe computer server(s) for a shipper based on the information receivedfrom the wireless tracker as well as a predefined list of shipmentlocations. A shipper may be a company or any entity that uses shipmentservices to deliver goods across geographical disparate shipmentlocations. For example, shipment locations for a shipper may correspondto manufacturing plant or research and development facilities.

In one embodiment, the wireless tracker 112 may determine its locationusing a GPS device or communicating with one or more GPS devices over anetwork. Further, the wireless tracker may include a battery such thatthe wireless tracker 112 regulates battery usage based on the locationof the wireless tracker 112. For example, when within a distancethreshold of the shipment origin or shipment destination, the managementmodule may request the communication module to determine a location ofthe wireless tracker 112 at frequent intervals so as to provide frequentupdates to a shipper on the location status of the shipment. However,beyond a distance threshold of the shipment origin and prior to adistance threshold of a shipment destination, frequent location statusupdates may not be needed by the shipper. Thus, the management modulemay not request the communication module to determine the location ofthe wireless tracker as frequently thereby regulating battery usage ofthe communication module. The location of the wireless tracker 112 maybe forwarded to the computer server(s) 102 from the wireless tracker112. Further, the computer server(s) may forward the location of thewireless tracker 112 to user devices (114-116).

In another embodiment, the wireless tracker 112 may include one or moresensors that are configurable. Further, the wireless tracker 112 mayaccess the receive sensor information from the one or more sensors. Inaddition, the wireless tracker 112 may determine a trigger event basedon the location of the wireless tracker 112 or sensor information. Inaddition, the wireless tracker 112 may send or transmit a notificationto the computer server 102 based on the trigger event. Further, thecomputer server(s) may forward the notification to user devices(114-116). Alternatively, the wireless tracker 112 may send or transmita sensor information to the computer server 102. Further, the computerserver(s) may forward the sensor information to user devices (114-116).

In additional embodiments, the wireless 112 tracker is configured toreceive and verify one or more codes to for a chain of custody of theshipment. In one embodiment, the wireless tracker receives a code at ashipment origin and receives a code at a shipment destination. Based onsuch authentication, the wireless tracker may transmit a notification tothe computer server(s) 102 verifying chain of custody.

In further embodiments, the wireless tracker 112 may determine that thelocation of the wireless tracker 112 is within a distance threshold ofthe shipment destination. In addition, the wireless tracker 112determine that a code was received within a time threshold. Thus, if thecode was received and verified by the authentication module of thewireless tracker 112 within both the distance threshold and the timethreshold, then the wireless tracker 112 may transmit a notification tothe computer server(s) 102 verifying chain of custody. However, if thecode was not received by the authentication module within either thedistance threshold or the time threshold, then the wireless tracker 112may transmit a notification to the computer server(s) 102 indicating abreak in chain of custody. Further, the computer server(s) may forwardthe verification notification or the break in chain of custodynotification to user devices (114-116).

For example, a shipment destination may be known. The wireless trackerdetermines that it is near the shipment destination. A distancethreshold may be configured as 500 meters. If an authentication code isreceived by the wireless tracker such that the wireless tracker islocated beyond 500 meters of the shipment destination, then anotification is generated by the wireless tracker indicating a break inthe chain of custody. The reason being that it may be likely that thepackage was stolen or otherwise compromised. However, if anauthentication code is received by the wireless tracker such that thewireless tracker is located within 500 meters of the shipmentdestination then the wireless tracker determines that chain of custodyis still intact. Further, is the authentication code is not providedwithin a time threshold of the wireless tracker being located within adistance threshold of the shipment destination, then a notification isgenerated by the wireless tracker indicating a break in the chain ofcustody. The reason being that it may be likely that the package may behidden, stolen, or otherwise compromised. However, if the authenticationcode is provided to the wireless tracker within both the distancethreshold of the shipment destination and the time threshold (and thecode is authenticated) then a notification is generated by the wirelesstracker that verifies chain of custody.

FIG. 2A is a functional block diagram of a wireless tracker 200, inaccordance with some embodiments. The wireless tracker 200 includes mailand response card box 201, communication module 210 and authenticationmodule 204 that is a bolted onto an integrated circuit board. A passiveradio frequency identification (RFID) tag 208 is affixed to the card box201 and programmed to have a unique identity/identification.

The wireless tracker 200 may be manufactured and operated in part by athird party manufacturer that may be used by a shipper or shipmentdelivery company. The third party manufacturer may own or operate one ormore computer servers to communicate with the wireless tracker 200 overone or more wireless communication networks using the communicationmodule 210. Further, the communication module 210 may be include one orcommunication interfaces configured to communicate over various wirelessnetworks such as GPS, Zigbee, Zwave, WiFi, cellular/mobile, Bluetooth,WiMAX or any other wireless communication network. In addition, thecommunication module may have an interface to communicate with otherdevices over a wired network or a wired interface such as an Ethernetcable or USC interface. Such wired connections may be implemented whenfirst configuring the wireless tracker 200 by the third partymanufacturer prior to use.

In some embodiments, the communication module 210 is configured todetermine a current location of the wireless tracker device at one ormore intervals wherein the one or more intervals are based on a deliveryroute of the shipment. For example, the communication module 210 may beconfigured (by the management module 212) to determine the location ofthe wireless tracker frequently within a distance threshold of theshipment origin or shipment destination. However, the communicationmodule 210 may be configured to determine the location of the wirelesstracker not as frequently beyond the distance threshold of the shipmentorigin and prior to the distance threshold of the shipment destination.Although such a configuration manages battery life, such a configurationalso avoids a situation when a user defines an alert condition when anasset enters and exits a specified geographic boundary that may not havebeen provided if the update interval was simply 30 minutes. In such ascenario, if the asset enters and exits the specified geographicboundary within 30 minutes then the tracing device fails to provide anupdate.

In an alternative embodiment, the management module 212 may receivesensor information from one or more sensors of the wireless tracker 200at different time intervals. However, the management module may requestsensor information for specific sensors only after the wireless trackerhas moved to a different location thereby regulating battery life. Forexample, the wireless tracker 200 may include a humidity sensor. Themanagement module 212 may be configured to only retrieve humidity sensorinformation when the wireless tracker has moved to a new locationinstead of at certain time intervals (e.g. every 30 minutes). Thus, thewireless tracker may stay at a certain location for a period of time(e.g. longer than 30 minutes) and the management module regulatesbattery usage/life by only gathering humidity sensor data when thewireless tracker has changed location. However, in other embodiments,the management module may request sensor information from sensors atcertain time intervals associated or not associated with the location ofthe wireless tracker.

The wireless tracker 200 may have one or more sensors that include butare not limited to, temperature sensors, humidity sensors, locationsensors, proximity sensors, accelerometers, acoustic, sound, vibration,automotive, transportation, chemical, electric current, electricpotential, magnetic, radio, environment, weather, moisture, flow, fluidvelocity, ionizing radiation, subatomic particles, navigationinstruments, position, angle, displacement, distance, speed,acceleration, optical light, imaging, photon, pressure, force, density,level, thermal, heat, temperature, proximity, and presence, etc. In oneembodiment the sensor may include a location sensor. In anotherembodiment, the location sensor may be the communication module 210communicating with a GPS device to retrieve location information of thewireless tracker 200. The management module 212 may be configured toconfigure the one or more sensors as well as receive sensor informationfrom the one or more sensors. Further, the management module 212 maydetermine a trigger event based on the location of the wireless trackerdevice and/or sensor information. In addition, the management module 212may transmit a notification to a computer server through thecommunication module based on the trigger event that is forwarded to auser device. Alternatively, sensor information may be provided to acomputer server to determine a trigger event or notify the user.Moreover, a trigger event includes, but is not limited to, a shipmentexiting shipment origin, delay at an intermediate location, travelingafter a delay, temperature deviation, humidity deviation, routedeviation, accident to delivery vehicle, tampering and shock to thedelivery vehicle. Sensor may include, but are not limited to,temperature sensors, humidity sensors, location sensors, proximitysensors, accelerometers, acoustic, sound, vibration, automotive,transportation, chemical, electric current, electric potential,magnetic, radio, environment, weather, moisture, flow, fluid velocity,ionizing radiation, subatomic particles, navigation instruments,position, angle, displacement, distance, speed, acceleration, opticallight, imaging, photon, pressure, force, density, level, thermal, heat,temperature, proximity, anti-tampering and presence. etc.

The authentication module 204 is used to track the chain of custody ofthe shipment associated with the wireless tracker 200. In oneembodiment, a shipper at a shipment origin may enter an authenticationcode into the authentication module 204. The authentication module 204verifies the code either locally or transfers the authentication code toa computer server for verification. Once the authentication code isverified, the shipment with the wireless tracker 200 is shipped to thedestination. In one embodiment, a packing slip inside the shipmentincludes another authentication code. Upon receiving the shipment at theshipment destination, a receiver of the shipment may open the shipmentto access the authentication code on the packing slip. Theauthentication code is entered into the authentication module 204 andverified (either locally or at a server). In addition, the verificationmay include determining whether the wireless tracker 200 is within adistance threshold of the shipment destination in accordance with theshipment order.

The authentication code may or may not be on a package slip. Further,the authentication code may include, but is not limited to, analphanumeric code (that can be randomly generated), a text code, agraphical code (such as bar code or QR code), and biometric code (suchas a fingerprint, signature, retinal scan, facial recognition, voicerecognition, etc.).

In further embodiments, the management module 212 may determine that thelocation of the wireless tracker 200 is within a distance threshold ofthe shipment destination. Further, the management module 212 maydetermine that a code was received by the authentication module 204within a time threshold. The distance threshold and time threshold maybe parameters for the wireless tracker that are configurable by ashipper or use of the wireless tracker 200. If the code was determinedto be received by the authentication module 204 within both the distancethreshold and time threshold then the management module 212 may transmita notification to a computer server through the communication module 210verifying chain of custody. Such a notification may be sent to a userdevice. However, if the code was not received by the authenticationmodule 204 either within a distance threshold or within a time thresholdthen the management module 212 transmit a notification to a computerserver through the communication module 210 indicating a break in thechain of custody that is forwarded to a user device.

In other embodiments, the wireless tracker 200 may determine tamperingsuch as separating the wireless tracker from the shipment. Suchdetermination may involve processing sensor information and otherparameters such as, but not limited to, ambient light, conductive tape,irregular motion detection, and orientation of the goods of theshipment.

In further embodiments, the wireless tracker 200 may implementmulti-dimensional tracking such as to determine and provide the abilityto configure the rules of tracking based on but not limited toif-else-while of various parameter like speed, altitude, temperature,pressure, location and change the behavior of tracking For example,international tracking intervals is changed while at sea, dynamicallychanging the tracking geo-boundaries and conditions.

In additional embodiments, the wireless tracker 200 can associated itsID (e.g. RFID) with a shipment order information such as order number,purchase order number, Serial Shipment Container Code (SSCC), Billing ofLading number, Lorry Receipt (LR) number, Shipment Manifest number andothers. Also, the wireless tracker is associated with the orderinformation of the shipment in-transit for easy lookup. The wirelesstracker may be associated with a wireless tracker identifier (e.g. RFID)such that the wireless tracker identifier is associated with shipmentorder information. Further, a wireless tracker 200 provides thecondition of the shipment in transit such as if the shipment is notwithin its shipping temperature, humidity, moisture limits, or if theshipment was moved from one transport carrier to another, or theshipment was not handled properly.

The RFID tag 208 is used to uniquely identify the wireless tracker 300.Thus, when the RFID tag is read at the shipment origin, the RFID tag isstored by the computer server and associated with the shipment. The RFIDtag 208 may be read again at the shipment destination to verify the RFIDtag is the same as the one read at the shipment origin. The presence ofRFID tag allows the wireless tracker owner to check in wireless trackerdevices received after use or check out wireless tracker devices tocustomers for use with ease. It also provides real time inventoryreconciliation and verification of device inventory at each wirelesstracker device storage location.

The mail and response card box 201 allows the receiver at the shipmentdestination to mail the wireless tracker 200 back to the shipment originor to a central location (e.g. shipper principal shipping location,third party manufacturer, etc.) to be reused for on another shipment.The sensor/power management module 212, in addition to the featuresdescribed herein, also manages the sensors and the battery power on thewireless tracker 200. This includes configuring the sensors and batteryas well as receiving the status of the sensors and battery.

Referring to FIG. 2B, a side of the wireless tracker 200 may have one ormore panels (216-226) as well as a foam pad 214. The foam pad 214 may beused to cushion or otherwise reduce vibration impacting the wirelesstracker 200. Further, the shipping address may be entered onto panel 216and associated prepaid postage affixed on panel 218. In addition, theReturn to Sender Address may be entered onto panel 224 and associatedprepaid postage affixed on panel 226. Advertisements may be affixed ontoto panels 220 and 224 for additional revenue for the shipper, shipmentdelivery company, or third party manufacturer of the wireless tracker200.

FIG. 3 is functional block diagram of a computer server used in trackinga shipment using a wireless tracker, in accordance with someembodiments. Such a server 305 may be used in a system shown in FIG. 1.The computer server 305 may include several different components such asa processor bank 310, storage device bank 315, one or more softwareapplications, which may be executed by a processor. Thus, thecombination of the software applications as well as the processor andany other hardware form specifically-configured modules 317. Thecomputer server 305 also has one or more communication interfaces(335-350). The processor bank 310 may include one or more processorsthat may be co-located with each other or may be located in differentparts of the computer server 305. The storage device bank 315 mayinclude one or more storage devices. Types of storage devices mayinclude electronic memory, optical memory, and removable storage media.The one or more modules 317 may include, but are not limited to,authentication/tracker management module 320, database management module322, notification/user input module 324, location processing module 326,sensor/trigger event processing module 328, and control module 330. Themodules 317 may be implemented by the one or more processors in theprocessor bank 310.

The computer server 305 and any other server described in the presentdisclosure may include a database stored in a storage device bank or maybe coupled to a database. Further, such a computer server may be part ofa computer server system described herein that may include one or morecomputer servers and one or more databases. In the present disclosure, acomputer server may, but not always, refer to embodiments that include acomputer server system having one or more computer servers and one ormore databases coupled to each other. The one or more computer serversmay be co-located with each other or distributed among differentlocations. Likewise, the one or more one or more databases may beco-located with each other or distributed among different locations. Infurther embodiments, some of the one or more computer servers may beco-located and coupled to the one or more databases while in additionalembodiments some of the one or more computer servers may be coupled tothe one or more databases each of which are placed in differentlocation. In still further embodiments, a computer server system mayrefer to at least one of a computer server and a database. Thecomponents shown in FIG. 3 may be located in one computer server or bedistributed among more than one computer server and/or databases.

The authentication/tracker management module 320 may perform, in someembodiments, the functions of the authentication module 204 and/or themanagement module 212 of a wireless tracker described herein. Thus, theauthentication/tracker management module 320 may be used in tracking thechain of custody of the shipment associated with a wireless tracker. Inone embodiment, a shipper at a shipment origin may enter anauthentication code into the authentication module of the wirelesstracker. Further, the wireless tracker (via its communication module)may transmit the authentication code to computer server 305. Theauthentication/tracker management module 320 verifies the authenticationcode and may provide the wireless tracker and/or a user device with anotification that the authentication code has been verified. Once, theauthentication code is verified, the shipment with the wireless trackeris shipped to a shipment destination. In one embodiment, a packing slipinside the shipment includes another authentication code. Upon receivingthe shipment at the shipment destination, a receiver of the shipment mayopen the shipment to access the authentication code on the packing slip.The authentication code is entered into the authentication module of thewireless tracker 204. Further, the wireless tracker (via itscommunication module) may transmit the authentication code to computerserver 305. The authentication/tracker management module 320 verifiesthe authentication code received at the shipment destination. Further, anotification may be sent to the wireless tracker or the user device thatthe chain of custody of the shipment has been verified.

The location processing module 326 may determine the location of theshipment based on one or more current locations received from thewireless tracker. Further, the location processing module 326 may accessa Global Positioning System (GPS) information (e.g. map information) aswell as geo-zone information surrounding one or more shipment locations(i.e. shipment origin, shipment destination, intermediate shipmentlocations). The location processing module 326 may process suchinformation to determine one or more trigger events. Such trigger eventsmay use the location processing module 326 to communicate with thenotification/user input module 324 to send a notification based on thetrigger event to a user device. In addition, once a location isdetermined by the location processing module 326, such location andassociated location information may be provided to theauthentication/tracker management module for further processing or thenotification/user input module 324 to send a notification to the userdevice.

For example, the location processing module 326 may receive a locationof the shipment from the wireless tracker that indicates that theshipment is at the shipment origin. Further, the location processingmodule 326 has access to information that there is geo-zone surroundingthe shipment origin. Subsequently, the location processing module 326may receive a location of the shipment from the wireless tracker thatindicates that the shipment has exited the geo-zone surrounding theshipment origin. The location processing module 326 determines that suchan event is a trigger event and thereby communicates with thenotification/user input module 324 to send a notification to the userdevice that the shipment has left the shipment origin.

In further embodiments, the authentication/tracker management module 320may receive the location of the wireless tracker from the locationprocessing module 326 and may determine that the location of thewireless tracker is within a distance threshold of the shipmentdestination. Further, the authentication/tracker management module 320may determine that a code was received by the authentication/trackermanagement module 320 within a time threshold. The distance thresholdand time threshold may be parameters that are configurable by a shipperor user of the wireless tracker. If the code was determined to bereceived and verified by the authentication/tracker management module320 within both the distance threshold and time threshold then theauthentication/tracker management 320 may transmit a notification (viathe notification/user input module 324) to the user device verifyingchain of custody. However, if the code was not received by theauthentication/tracker management module 320 either within a distancethreshold or within a time threshold then the authentication/trackermanagement module 320 transmit a notification (via the notification/userinput module 324) to the user device indicating a break in the chain ofcustody.

In some embodiments, the authentication/tracker management module 320 isconfigured to determine a current location of the wireless trackerdevice at one or more intervals wherein the one or more intervals arebased on a delivery route of the shipment. For example, theauthentication/tracker management module 320 may be configure thewireless tracker to determine its location frequently within a distancethreshold of the shipment origin or shipment destination. However, theauthentication/tracker management module 320 may configure the wirelesstracker to determine its location not as frequently beyond the distancethreshold of the shipment origin and prior to the distance threshold ofthe shipment destination. Although such a configuration manages batterylife of the wireless tracker, such a configuration also avoids asituation when a user defines an alert condition when an assetassociated with the wireless tracker enters and exits a specifiedgeographic boundary that may not have been provided if the updateinterval was simply 30 minutes. In such a scenario, if the asset entersand exits the specified geographic boundary within 30 minutes then thetracing device fails to provide an update.

In other embodiments, the wireless tracker provides an update regardingremaining battery life of the wireless tracker to the computer server305. Further, the remaining battery life nay be forwarded to a userdevice by the notification/user input module 324. Theauthentication/tracker management module 320 may determine to adjust(automatically or based on user input in response to the notification ofremaining battery life) the frequency of location and sensor updates ofthe wireless tracker to better manage the remaining battery life andprovides such configuration information to the wireless tracker,accordingly. Further based on a route of the wireless tracker (the routemay be preprogrammed into the computer server 305 or determined by thecomputer server 305 based on one or more location updates provided bythe wireless tracker), may provide configuration information to regulatethe battery life of the wireless tracker. In additional embodiments, thecomputer server 305 may receive and process one or more location updatesfrom the wireless tracker to determine a route deviation of the wirelesstracker. The computer server may provide additional configurationinformation to further regulate the battery life based on the routedeviation.

In further embodiments, the computer server 305 may receive the currentlocation of the wireless tracker and the location processing module 326determines that the current location of the wireless tracker is ashipment destination. The authentication/tracker management module maydetermine a return address of the wireless tracker based on logisticsinformation and send a return address to a shipment destination devicesuch as a computer, smartphone, or printer allowing shipment destinationpersonal to print a label with the return address and postage to affixto the wireless tracker and returned to the wireless tracker deviceowner. In such embodiments, the logistics information may be processedto determine that the wireless tracker should be returned to theshipment origin. Alternatively, the logistics information may beprocessed to determine that the wireless tracker should be sent toanother location that it would be more useful.

In other embodiments, the computer server 305 may determine a shipmentdestination for a wireless tracker. The authentication/trackermanagement module may determine a return address of the wireless trackerbased on logistics information and generate a label with a returnaddress configured to be coupled to one or more panels of the wirelesstracker. In such embodiments, the logistics information may be processedto determine that the wireless tracker should be returned to theshipment origin. Alternatively, the logistics information may beprocessed to determine that the wireless tracker should be sent toanother location that it would be more useful. In still anotheralternative, logistics information may be process to determine that thewireless tracker can be used with a new shipment originating from theshipment destination and need not be returned to another location uponarrival.

In additional embodiments, the computer server 305 may determinetampering of the wireless tracker such as separating the wirelesstracker from the shipment. Such determination may involve processingsensor information and other parameters such as, but not limited to,ambient light, conductive tape, irregular motion detection, andorientation of the goods of the shipment.

In further embodiments, the computer server 305 may implementmulti-dimensional tracking of the wireless tracker such as to determineand provide the ability to configure the rules of tracking based on butnot limited to if-else-while of various parameter like speed, altitude,temperature, pressure, location and change the behavior of tracking Forexample, international tracking intervals is changed while at sea,dynamically changing the tracking geo-boundaries and conditions.

In additional embodiments, the wireless tracker can associated its ID(e.g. RFID) with a shipment order information such as order number,purchase order number, Serial Shipment Container Code (SSCC), Billing ofLading number, Lorry Receipt (LR) number, Shipment Manifest number andothers, and provides such information to the computer server for furtherprocessing and notification to the user. Also, the wireless tracker isassociated with the order information of the shipment in-transit foreasy lookup. Further, a wireless tracker provides to the computer server305 the condition of the shipment in transit such as if the shipment isnot within its shipping temperature, humidity, moisture limits, or ifthe shipment was moved from one transport carrier to another, or theshipment was not handled properly such that the computer server notifiesor takes action on such information.

The database management module 322 manages the storage and access ofinformation related to the operation of the wireless tracker or shipmentinformation. For example, the database management module 322 may storeone or more locations of the shipment that is provided by a wirelesstracker. In addition, the database management module 322 may storeinformation from one or more sensors coupled to and provided by thewireless tracker. Such location information and sensor information maybe used to determine a trigger event to notify the shipper.

The notification/user input module 324 may perform several differentfunctions. One such function may be to receive user input from a userdevice. Such user input may be configuration parameters for operatingthe wireless tracker. These may include specified times or locations toquery the wireless tracker for sensor information, location, or otherstatus information. Another function of the notification/user inputmodule 424 to provide a notification based on a trigger event to theuser device. A notification may be generated based on a trigger eventdetermined by the different modules of the computer server 305 such as,but not limited to, the authentication/tracker module 320, locationprocessing module 326, and the sensor/trigger event processing module328.

The sensor/trigger event processing module 328 may receive sensorinformation from the wireless tracker. Further, the sensor/trigger eventprocessing module may determine certain trigger events based on thereceived sensor information and send a notification (via thenotification/user input module 324) to a user device. In addition, thesensor/trigger event processing module may be programmed or receiveconfiguration parameters to be forwarded to the wireless tracker for itsoperation. For example, the configuration parameters may include timeand location of providing location and other sensor information as wellas at which time periods to operate the different sensors to regulatebattery life.

In some embodiments, the computer server 305 may receive a notificationfrom the wireless tracker. Further, the computer server 305 may processthe information in the notification based on configuration parametersand transmit information to the wireless tracker to take some furtheraction. For example, a user may be tracking a shipment traveling fromLas Vegas to Washington, D.C. (by air transport) with an intermediatestop in Dallas during the winter season. However, the computer server305 may receive a notification that the shipment was diverted to have anintermediate stop at Chicago instead of Dallas due to severe weatherconditions surrounding the Dallas area. The computer server 305 may haveconfiguration information that includes that the shipment may betemperature sensitive and cannot be in environment less than 32 degreesFahrenheit. Further, the computer server may have additionalconfiguration information that if the shipment is at a location above acertain latitude or in a certain geographical area, to request thewireless tracker take a temperature reading with its temperature sensorand provide such temperature sensor information to the computer server305. Further, if the computer server 305 is notified that thetemperature is less than 32 degrees Fahrenheit, then the computer servermay send a notification to shipper personnel to place the shipment in awarmer environment.

The control module 330 includes software and hardware functions thatassist in performing certain tasks for the computer serve 305 such asproviding access to a communication link (e.g. wired, wireless,Bluetooth, infra-red, RF, etc.), executing an operating system, managingsoftware drivers for peripheral components, and processing information.In addition, the control module 330 may also include software driversfor peripheral components, user interface computer programs, debuggingand troubleshooting software tools. Also, the control module 330 mayinclude an operating system. Such operating systems are known in the artfor computer server 305 but may also include computer operating systems(e.g. Windows, Linux, UNIX, and MacOS, etc.).

Each of the communication interfaces (335-350) may be software orhardware associated in communicating to other devices. The communicationinterfaces (335-350) may be of different types that include a userinterface, USB, Ethernet, WiFi, WiMax, wireless, optical, cellular, orany other communication interface coupled to a communication network.One or more of the communication interfaces (335-350) may be coupled toa user interface known in the art.

An intra-device communication link 355 between the processor bank 310,storage device bank 315, modules 317, and communication interfaces(335-350) may be one of several types that include a bus or othercommunication mechanism.

FIG. 4 is functional block diagram of a user computing device 405 forproviding configuration information to a wireless tracker as well asreceiving trigger event notifications based on wireless trackerinformation, in accordance with some embodiments. Such a user device 405may be used in a system shown in FIG. 1. The user device 405 may includeseveral different components such as a processor bank 410, storagedevice bank 415, one or more software applications, which may beexecuted by a processor. Thus, the combination of the softwareapplications as well as the processor and any other hardware formspecifically-configured modules 417. The user device 405 also has one ormore communication interfaces (435-450). The processor bank 410 mayinclude one or more processors that may be co-located with each other ormay be located in different parts of the shipper computing device 405.The storage device bank 415 may include one or more storage devices.Types of storage devices may include electronic memory, optical memory,and removable storage media. The one or more modules 417 may include,but are not limited to, a configuration module 420 and a notificationdisplay/user input module 424. The modules 417 may be implemented by theone or more processors in the processor bank 410. Examples of userdevices, include, but are not limited to, desktop computers, laptopcomputers, tablet computers, smartphones, and any other computingdevices.

A user may provide configuration information for a wireless tracker.Such user input may be entered into a user interface (one or of thecommunication interfaces (435-450)) and may be received by thenotification display/user input module 424. Such configurationinformation may include time and location of providing location andother sensor information of the wireless tracker as well as at whichtime periods to operate the different sensors of the wireless tracker toregulate its battery life. The configuration module 420 may process suchconfiguration information and determine whether such user input mayconflict with current operation of the wireless tracker or with a priorconfiguration of the wireless tracker. If so, the configuration modulemay provide a notification on the notification display 424. If not, theconfiguration information may then transmitted to one or more computerservers over one of the communication interfaces (435-450). Also, thenotification display/user input module 424 may receive a notificationfrom the computer server(s) via the communication interface (435-450)and display such a notification on a user interface.

In some embodiments, the user device 405 may receive a notification fromthe wireless tracker (via a computer server) and present thenotification to a user on a user device display. Further, the user mayenter information into a user device user interface that may betransmitted to the wireless tracker (via the computer server) to takesome further action. For example, a user may be tracking a shipmenttraveling from Las Vegas to Washington, D.C. (by air transport) with anintermediate stop in Dallas during the winter season. However, the userdevice 405 may receive a notification that the shipment was diverted tohave an intermediate stop at Chicago instead of Dallas due to severeweather conditions surrounding the Dallas area. The shipment may betemperature sensitive and cannot be in environment less than 32 degreesFahrenheit. The user may input information that is transmitted to thewireless tracker (via the computer server) to request the wirelesstracker take a temperature reading with its temperature sensor andprovide such temperature sensor information to the user device (via thecomputer server). Further, if the user is notified that the temperatureis less than 32 degrees Fahrenheit, then the user may enter informationto the computer server to notify shipper personnel to place the shipmentin a warmer environment.

Each of the communication interfaces (435-450) may be software orhardware associated in communicating to other devices. The communicationinterfaces (435-450) may be of different types that include a userinterface, USB, Ethernet, WiFi, WiMax, wireless, optical, cellular, orany other communication interface coupled to a communication network.One or more of the communication interfaces (435-450) may be coupled toa user interface known in the art.

An intra-device communication link 455 between the processor bank 410,storage device bank 415, modules 417, and communication interfaces(435-450) may be one of several types that include a bus or othercommunication mechanism.

FIGS. 5A-5C are flowcharts that illustrates methods for using a wirelesstracker with a shipment, in accordance with some embodiments. Referringto FIG. 5A, method 500 includes determining, by a communication moduleof a wireless tracker associated with a shipment, a location of thewireless tracker device, as shown in block 502. Further, the method 500includes regulating, by a management module of the wireless tracker, abattery of the wireless tracker based on the location of the wirelesstracker device, as shown in block 506. In addition, the method 500includes receiving, by the authentication module, a code at a shipmentorigin, as shown in block 504. Moreover, the method includes receiving,by the authentication module, a code a shipment destination, at a block508. Also, the method 500 includes determining, by the managementmodule, that the location of the wireless tracker device is within adistance threshold of the shipment destination, as shown in block 510.Further, the method 500 includes determining that a code was notreceived by the authentication module within a time threshold, as shownin block 514. In addition, the method 500 includes transmitting anotification to a computer server through the communication moduleindicating a break in the chain of custody, as shown in block 512.Moreover, the method 500 includes determining, by the management module,that the location of the wireless tracker device is not within adistance threshold of the shipment destination, as shown in block 510.Also, the method 500 includes transmitting, by the management module, anotification to a computer server through the communication moduleindicating a break in the chain of custody, as shown in block 512. Incertain embodiments, the authentication code may have received the codeeither not within the distance threshold of the shipment destination ornot within the time threshold as configured. In either scenario, themethod 500 includes transmitting a break in chain of custodynotification to a computer server and forwarded to a user device, asshown in block 512. However, if a code is received and verified within adistance threshold of the shipment destination and within a configuredtime threshold (and the code is authenticated) then the method 500includes verifying, by the authentication module, the one or more codes,for a chain of custody of the shipment and transmitting a chain ofcustody verification notification to a computer server and forwarded toa user device, as shown in block 516.

Referring to FIG. 5B, the method 520 includes configuring, by themanagement module, one or more sensors of the wireless tracker, as shownin block 522. Further, the method 520 includes receiving, by themanagement module, sensor information from the one or more sensors, asshown in block 524. In addition, the method 520 includes transmitting anotification based on the sensor information to a computer server andforwarded to a user device, as shown in block 526.

Referring to FIG. 5C, the method 530 includes determining a location ofthe wireless tracker, as shown in block 532. Further, the method 530includes receiving, by the management module, sensor information fromthe one or more sensors, as shown in block 534. In addition, the method530 includes determining, by the management module, a trigger eventbased on at least one of the location of the wireless tracker device andsensor information, as shown in block 536. Moreover, the method 530includes transmitting or sending, by the communication module, anotification to a computer server through the communication module basedon the trigger event and forwarded to a user device, as shown in block538.

Persons of ordinary skill in the art understand that the steps ofmethods described herein can be implemented in any order and not limitedto the order discussed in the present disclosure. Further, functionsimplemented by modules within the computer server(s) described hereinmay also be implemented in the modules of the wireless tracker. Inaddition, functions implemented by the module of the wireless trackermay also be implemented by the computer server(s). Moreover, functionsimplemented by modules within the computer server(s) described hereinmay also be implemented in the modules of the user device. Also,functions implemented by modules within the user device described hereinmay also be implemented in the modules of the computer server(s).

In the foregoing specification, specific embodiments have beendescribed. However, one of ordinary skill in the art appreciates thatvarious modifications and changes can be made without departing from thescope of the invention as set forth in the claims below. Accordingly,the specification and figures are to be regarded in an illustrativerather than a restrictive sense, and all such modifications are intendedto be included within the scope of present teachings.

The benefits, advantages, solutions to problems, and any element(s) thatmay cause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as a critical, required, or essentialfeatures or elements of any or all the claims. The invention is definedsolely by the appended claims including any amendments made during thependency of this application and all equivalents of those claims asissued.

Moreover in this document, relational terms such as first and second,top and bottom, and the like may be used solely to distinguish oneentity or action from another entity or action without necessarilyrequiring or implying any actual such relationship or order between suchentities or actions. The terms “comprises,” “comprising,” “has”,“having,” “includes”, “including,” “contains”, “containing” or any othervariation thereof, are intended to cover a non-exclusive inclusion, suchthat a process, method, article, or apparatus that comprises, has,includes, contains a list of elements does not include only thoseelements but may include other elements not expressly listed or inherentto such process, method, article, or apparatus. An element proceeded by“comprises . . . a”, “has . . . a”, “includes . . . a”, “contains . . .a” does not, without more constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises, has, includes, contains the element. The terms“a” and “an” are defined as one or more unless explicitly statedotherwise herein. The terms “substantially”, “essentially”,“approximately”, “about” or any other version thereof, are defined asbeing close to as understood by one of ordinary skill in the art, and inone non-limiting embodiment the term is defined to be within 10%, inanother embodiment within 5%, in another embodiment within 1% and inanother embodiment within 0.5%. The term “coupled” as used herein isdefined as connected, although not necessarily directly and notnecessarily mechanically. A device or structure that is “configured” ina certain way is configured in at least that way, but may also beconfigured in ways that are not listed.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

We claim:
 1. A wireless tracker device associated with a shipment,comprising: a communication module configured to determine a route ofthe wireless tracker device; a battery; a management module configuredto regulate battery usage based on the route of the wireless trackerdevice.
 2. The wireless tracker of claim 1, wherein the wireless trackerprovides an update regarding remaining battery life of the wirelesstracker.
 3. The wireless tracker of claim 1, wherein the managementmodule regulates battery usage based on a route deviation of thewireless tracker.
 4. The wireless tracker of claim 1, wherein thewireless tracker is associated with a wireless tracker identifier suchthat the wireless tracker identifier is associated with shipment orderinformation.
 5. The wireless tracker device of claim 1, furthercomprising: one or more panels that include at least one of a recipientaddress, and recipient postage such that the wireless tracker isdelivered to the recipient address.
 6. The wireless tracker device ofclaim 1, wherein the communication module is configured to determine acurrent location of the wireless tracker device at one or more intervalswherein the one or more intervals are based on a delivery route of theshipment.
 7. The wireless tracker device of claim 1, further comprising:an authentication module configured to receive and verify one or morecodes for a chain of custody of the shipment.
 8. The wireless trackerdevice of claim 4, wherein the authentication module receives a code ata shipment origin.
 9. The wireless tracker device of claim 4, whereinthe authentication module receives a code at a shipment destination. 10.The wireless tracker device of claim 4, wherein the management module isconfigure to: determine that the location of the wireless tracker deviceis within a distance threshold of the shipment destination; determinethat a code was not received by the authentication module within a timethreshold; transmitting a notification to a computer server through thecommunication module indicating a break in the chain of custody.
 11. Thewireless tracker device of claim 4, wherein the management module isconfigure to: determine that the location of the wireless tracker deviceis not within a distance threshold of the shipment destination;determine that a code was received by the authentication module within atime threshold; transmitting a notification to a computer server throughthe communication module indicating a break in the chain of custody. 12.The wireless tracker device of claim 1, further comprising: one or moresensors; the management module configured to configure the one or moresensors and receive sensor information from one or more sensors.
 13. Thewireless tracker device of claim 9, wherein the management module isconfigured to: determine a trigger event based on at least one of thelocation of the wireless tracker device and sensor information; send anotification to a computer server through the communication module basedon the trigger event.
 14. A method, comprising: determining, by acommunication module of a wireless tracker associated with a shipment, alocation of the wireless tracker device; regulating, by a managementmodule of the wireless tracker, a battery based on the location of thewireless tracker device.
 15. The method of claim 14, wherein thewireless tracker provides an update regarding remaining battery life ofthe wireless tracker.
 16. The method of claim 14, wherein the managementmodule regulates battery usage based on a route deviation of thewireless tracker.
 17. The method of claim 14, wherein the wirelesstracker is associated with a wireless tracker identifier such that thewireless tracker identifier is associated with shipment orderinformation.
 18. The method of claim 14, wherein the wireless trackerdevice includes one or more panels that include at least one of a senderaddress, sender postage, recipient address, and recipient postage suchthat the wireless tracker is delivered to the recipient address.
 19. Themethod of claim 14, wherein the communication module is configured todetermine a current location of the wireless tracker device at one ormore intervals wherein the one or more intervals are based on a deliveryroute of the shipment.
 20. The method of claim 14, further comprising:receiving, by an authentication module of the wireless tracker, one ormore codes; verifying, by the authentication module, the one or morecodes, for a chain of custody of the shipment.
 21. The method of claim20, further comprising receiving, by the authentication module, a codeat a shipment origin.
 22. The method of claim 20, further comprisingreceiving, by the authentication module, a code a shipment destination.23. The method of claim 20, further comprising: determining, by themanagement module, that the location of the wireless tracker device iswithin a distance threshold of the shipment destination; determiningthat a code was not received by the authentication module within a timethreshold; transmitting a notification to a computer server through thecommunication module indicating a break in the chain of custody.
 24. Themethod of claim 20, further comprising: determining, by the managementmodule, that the location of the wireless tracker device is not within adistance threshold of the shipment destination; determining, by themanagement module, that a code was received by the authentication modulewithin a time threshold; transmitting, by the management module, anotification to a computer server through the communication moduleindicating a break in the chain of custody.
 25. The method of claim 14,further comprising: configuring, by the management module, one or moresensors of the wireless tracker; receiving, by the management module,sensor information from the one or more sensors.
 26. The method of claim25, further comprising: determining, by the management module, a triggerevent based on at least one of the location of the wireless trackerdevice and sensor information; sending, by the communication module, anotification to a computer server through the communication module basedon the trigger event.
 27. A system, comprising: a wireless trackerdevice associated with a shipment, having: a communication moduleconfigured to determine a location of the wireless tracker device; abattery; a management module configured to regulate battery usage basedon the location of the wireless tracker device.
 28. The system of claim27, wherein the wireless tracker provides an update regarding remainingbattery life of the wireless tracker.
 29. The system of claim 27,wherein the management module regulates battery usage based on a routedeviation of the wireless tracker.
 30. The system of claim 27, whereinthe wireless tracker is associated with a wireless tracker identifiersuch that the wireless tracker identifier is associated with shipmentorder information.
 31. The system of claim 27, wherein the wirelesstracker device includes one or more panels that include at least one ofa recipient address, and recipient postage such that the wirelesstracker is delivered to the recipient address.
 32. The system of claim27, further comprising: a computer server configured to: determine aroute of the wireless tracker; determine a shipment destination based onthe route; determine a return address of the wireless tracker based onlogistics information; generate a return address on a label configuredto couple to one or more panels of the wireless tracker.
 33. The systemof claim 27, wherein the communication module is configured to determinea current location of the wireless tracker device at one or moreintervals wherein the one or more intervals are based on a deliveryroute of the shipment.
 34. The system of claim 27, wherein the wirelesstracker includes an authentication module configured to receive andverify one or more codes to for a chain of custody of the shipment. 35.The system of claim 34, wherein the authentication module receives acode at a shipment origin.
 36. The system of claim 34, wherein theauthentication module receives a code at a shipment destination.
 37. Thesystem of claim 34, further comprising a computer server coupled to thewireless tracker; wherein the management module of the wireless trackeris configure to: determine that the location of the wireless trackerdevice is within a distance threshold of the shipment destination;determine that a code was not received by the authentication modulewithin a time threshold; transmitting a notification to the computerserver through the communication module indicating a break in the chainof custody.
 38. The system of claim 37, further comprising a user devicethat receives the notification indicating a break in the chain ofcustody.
 39. The system of claim 34, further comprising a computerserver coupled to the wireless tracker; wherein the management module isconfigure to: determine that the location of the wireless tracker deviceis not within a distance threshold of the shipment destination;determine that a code was received by the authentication module within atime threshold; transmitting a notification to the computer serverthrough the communication module indicating a break in the chain ofcustody.
 40. The system of claim 39, further comprising a user devicethat receives the notification indicating a break in the chain ofcustody.
 41. The system claim 27, wherein the wireless tracker includesone or more sensors and wherein the management module configured toconfigure the one or more sensors and receive sensor information fromone or more sensors.
 42. The system of claim 41, further comprising acomputer server coupled to the wireless tracker; wherein the managementmodule of the wireless tracker is configured to: determine a triggerevent based on at least one of the location of the wireless trackerdevice and sensor information; send a notification to the computerserver through the communication module based on the trigger event;


43. The system of claim 42, further comprising a user device thatreceives the notification based on the trigger event.